Policy-based printing system using split-printing methods

ABSTRACT

A policy-based printing system is implemented to allow access to a private domain to print using a public domain. The private domain includes private servers that store documents. The public domain includes servers and a printing device. A public policy server uses a domain list and a protocol connection with a private authentication server to validate a user and identify which private domain to access. The public policy server receives requests from the printing device to process a print job of a document in the private domain. The public server may associate a public personal identification number (PIN) with a corporate PIN for the printing operations. In the event of split printing, the public server generates another public PIN for use with another printing device.

FIELD OF THE INVENTION

The present invention relates to a system of private and public servers that implement policy-based printing operations. The system includes a public and private network that supports the policy used for printing operations, wherein the policy is implemented using a private server in the private network having split printing methods to print a document over two or more printing devices.

DESCRIPTION OF THE RELATED ART

Existing policy-based printing systems mostly operate within a closed private domain environment. Print data submitted by users may be only accessible within a single domain environment. Some users, such as on-the-go users including insurance and real estate agents, sales executives, lawyers, and company executives, require the capability to access printing data beyond an office environment. These users travel extensively and find themselves needing to print in public locations, such as convenience stores, libraries, airports, copy and printing service stores, and the like. At these locations, the users may not reliably access the printing data. Further, these public locations may not support policy-based printing.

SUMMARY OF THE INVENTION

A policy-based printing method is disclosed. The policy-based printing method includes receiving a corporate personal identification number (PIN) at a public server. The corporate PIN corresponds to a document stored on a private server. The policy-based printing method also includes applying a policy to allow a print job for the document based on the corporate PIN. The policy-based printing method also includes generating a first public PIN corresponding to the corporate PIN at the public server. The policy-based printing method also includes sending the first public PIN to a mobile application on a mobile device. The policy-based printing method also includes receiving the first public PIN at the public server from a first printing device. The policy-based printing method also includes sending the document corresponding to the corporate PIN to the first printing device in response to the first public PIN. The policy-based printing method also includes printing the document at the first printing device. The policy-based printing method also includes stopping the printing job of the document. The policy-based printing method also includes generating a second public PIN at the public server corresponding to the corporate PIN. The second public PIN refers to an unprinted portion of the document. The policy-based printing method also includes receiving the second public PIN at the public server from a second printing device. The policy-based printing method also includes sending the unprinted portion of the document to the second printing device. The policy-based printing method also includes printing the unprinted portion of the document at the second printing device.

A policy-based printing method is disclosed. The policy-based printing method includes sending a corporate personal identification number (PIN) entered into a mobile application on a mobile device to a public server. The corporate PIN corresponds to a document stored on a private server connected to the public server. The policy-based printing method also includes applying a policy stored at the private server to determine whether to print the document corresponding to the corporate PIN. The policy-based printing method also includes receiving a first public PIN at the mobile application from the public server to print the document. The first public PIN corresponds to the public PIN. The policy-based printing method also includes receiving the first public PIN at the public server from a first printing device. The policy-based printing method also includes printing a first portion of the document at the first printing device. The policy-based printing method also includes determining that the first printing device is not available. The policy-based printing method also includes receiving a second public PIN at the mobile application from the public server. The second public PIN corresponds to the public PIN. The policy-based printing method also includes receiving the second public PIN at the public server from a second printing device. The policy-based printing method also includes printing a second portion of the document at the second printing device.

A policy-based printing system is disclosed. The policy-based printing system includes a mobile device configured to execute a mobile application. The policy-based printing system includes a private server storing a document and a corporate personal identification number (PIN) corresponding to the document. A policy is applied to determine whether to print the document upon receipt of the corporate PIN at the private server. The corporate PIN is provided to the mobile application. The policy-based printing system also includes a public server connected to the private server and configured to send the corporate PIN upon receipt from the mobile device. The public server generates a first public PIN upon receipt of the corporate PIN from the mobile application and sends the first public PIN to the mobile application. The policy-based printing system also includes a first printing device to send the first public PIN to the public server and to print the document received from the public server. The printing device indicates to the public server that printing operations are stopped and an unprinted portion of the document remains. The public server generates a second public PIN for the unprinted portion of the document and sends the second public PIN to the mobile application. The policy-based printing system also includes a second printing device to send the second public PIN to the public server and to print the unprinted portion of the document.

A policy-based printing method is disclosed. The method includes receiving a corporate personal identification number (PIN) at a public server. The corporate PIN corresponds to a document stored on a private server. The method also includes generating a first public PIN corresponding to the corporate PIN at the public server. The method also includes receiving the first public PIN at the public server from a first printing device. The method also includes sending the document corresponding to the corporate PIN to the first printing device in response to the first public PIN. The method also includes printing the document at the first printing device. The method also includes stopping the print job of the document. The method also includes generating a second public PIN at the public server corresponding to the corporate PIN. The second public PIN refers to an unprinted portion of the document. The method also includes receiving the second public PIN at the public server from a second printing device. The method also includes sending the unprinted portion of the document to the second printing device. The method also includes printing the unprinted portion of the document at the second printing device.

BRIEF DESCRIPTION OF THE DRAWINGS

Various other features and attendant advantages of the present invention will be more fully appreciated when considered in conjunction with the accompanying drawings.

FIG. 1 depicts a system to implement policy-based printing on a printing device according to the disclosed embodiments.

FIG. 2 illustrates a block diagram of components of the printing device used in conjunction with the authentication system according to the disclosed embodiments.

FIG. 3 illustrates a flow diagram for implementing a policy-based printing system according to the disclosed embodiments.

FIG. 4A illustrates a domain list for use within the policy-based printing system according to the disclosed embodiments.

FIG. 4B illustrates a policy for use within the policy-based printing system according to the disclosed embodiments.

FIG. 5 illustrates a block diagram of servers and data used within the policy-based printing system according to the disclosed embodiments.

FIG. 6 illustrates a flowchart for printing at a printing device within the policy-based printing system according to the disclosed embodiments.

FIG. 7 illustrates a flowchart for implementing a policy-based printing system in a public domain according to the disclosed embodiments.

FIG. 8 illustrates a flowchart for implementing a policy-based printing system using tokens according to the disclosed embodiments.

FIG. 9 illustrates a flowchart for selecting a plurality of print jobs from a plurality of private domains for printing in a public domain according to the disclosed embodiments.

FIG. 10 illustrates a policy-based printing system to implement policy-based printing using a private server according to the disclosed embodiments.

FIG. 11 illustrates a policy-based printing system implementing split printing between two printing devices according to the disclosed embodiments.

FIG. 12 illustrates a block diagram of data within a public server for split printing according to the disclosed embodiments.

FIG. 13 illustrates a flowchart for printing using a public server in a policy-based system according to the disclosed embodiments.

FIG. 14 illustrates a flowchart for performing split printing using the public server and a second printing device according to the disclosed embodiments.

FIG. 15 illustrates a flowchart for receiving a public PIN at a printing device according to the disclosed embodiments.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to specific embodiments of the present invention. Examples of these embodiments are illustrated in the accompanying drawings. Numerous specific details are set forth in order to provide a thorough understanding of the present invention. While the embodiments will be described in conjunction with the drawings, it will be understood that the following description is not intended to limit the present invention to any one embodiment. On the contrary, the following description is intended to cover alternatives, modifications, and equivalents as may be included within the spirit and scope of the appended claims. Numerous specific details are set forth in order to provide a thorough understanding of the present invention.

The disclosed embodiments use an authentication server, a policy server, a file server, a network enabled printing device, and a public domain server. At the printing device, a user may provide authentication information, such as a username or password. The authentication information is transmitted from the device to a public domain server that processes the username for domain information. The domain information is matched to a domain on record and a private server is identified that can handle the domain authentication. The public domain server, through a direct connection to the private server, will go through a series of steps to obtain an authentication token, a policy applicable to the user, a job list of the user, and the job binary data for printing a print job on the printing device.

FIG. 1 depicts a system 100 to implement policy-based printing on a printing device 104 according to the disclosed embodiments. System 100 includes network 102 which exchanges data between the public and private domains within system 100. System 100 allows a user to retrieve a print job having job binary data 140 from a private domain server to print on printing device 104. Printing device 104 may be any device that processes the binary data to generate an electronic document that is then printed or accessed by the user. Printing device 104 also may be known as an image forming apparatus or a multi-functional printer. For example, printing device 104 may print on a sheet of paper the document generated from binary data 140. Alternatively, printing device 104 may display the electronic document to the user. Printing device 104 also may store the binary data for the print job. Printing device includes engine 106, which performs many of the operations to print, scan, store, modify, and the like. Printing device 104 and engine 106 are disclosed in greater detail below with reference to FIG. 2.

System 100 include public domain 110 and private domains 120 and 130. Public domain 110 may represent a collection of public servers and devices linked to network 102. In some embodiments, these servers are cloud servers. Public domain 110 also may be known as a public network of the public servers. Public domain 110 is accessible by printing device 104. Additional printing devices may connect to public domain 110, such shown by printing device 105. The printing devices may be located in public places, such as convenience stores, libraries, printing and copying stores and kiosks, and the like. Users may access the printing devices and, in turn, the servers within public domain 110. The users may need to validate their ability to access public domain 110 through a connected printing device.

Public domain 110 includes public policy server 112. Public policy server 112 interacts with private domains 120 and 130 as well as printing devices 104 and 105. Public policy server 112 may act as the middle man between public domain 110 and the private domains. Public policy server 112 may generate and store tokens used to implement the policy-based operations disclosed below. It also may store and allow access to a policy 142 received from a private domain, upon request. Policy 142, disclosed in greater detail below, outlines what a user can and cannot do when printing to printing device 104 from a private domain.

Public file server 114 is connected to public policy server 112. Public file server 114 may store or host binary data 140 for print job from a private domain. Printing device 104 may retrieve binary data 140 securely for a print job. In some embodiments, printing device 104 does so through public policy server 112. Public file server 114 also may receive binary data 140 from a server in a private domain, as disclosed below.

System 100 includes private domains 120 and 140. System 100 may include additional private domains, not shown here. Each private domain may include a plurality of private servers that are protected by a firewall from access from network 102. For example, private domain 120 includes firewall 122. Firewall 122 may be a software or hardware device that filters data and information coming over network 102 to private domain 120 for malicious or unauthorized access. If an incoming packet of data is flagged by the filters in firewall 122, then it is not allowed through to private domain 120. Firewall 132 may serve the same function for private domain 130.

Private domain 120 includes private authentication server 124, private job server 126, and private policy server 128. Private domain 130 includes private authentication server 134, private job server 126, and private policy server 128. The servers for private domain 120 are disclosed below, but their functionality may apply to the servers in private domain 130. Further, additional servers may be in a private domain and used securely to exchange information over network 102.

Private authentication server 124 is a private domain server that will provide authentication and authorize a user to prove his/her identify. Private authentication server 124 may be the main server that connects the private and public domain information exchange. In some embodiments, private authentication server 124 establishes a protocol connection 144 with public policy server 112 to provide a domain list 146 for access to private domain 120. Private authentication server 124 also verifies a user trying to access private domain 120 using public policy server 112.

Private job server 126 is a private domain server that stores all the binary data for the job files, or print jobs. When a user wants to print out a job file at printing device 104, private job server 126 should be queried in order to retrieve binary data 140 to generate the print job. Private job server 126 may forward binary data 140 to public file server 114 according to policy 142.

Private policy server 128 is a private domain server that hosts or stores all the policies, such as policy 142, related to a user. When printing device 104 attempts to perform any function, it should request private policy server 128 determine whether the user is allowed to do so. Private policy 128 may do the determination via public policy server 112.

The disclosed embodiments allow access to private servers from a public domain or to print on printing device 104 within a public network. An intranet application may do the authentication and job spooling so users need to authenticate printing device 104 before use. A policy may be associated with where a user can print, what kind of paper, number of pages, and the like. For example, some users may want to print from a public location, such as a convenience store, and want to access a private server that stores the print jobs. They would need access from network 102.

In some embodiments, public policy server 112 is a cloud server. Public policy server 112 may not be able to do accounting policy management to determine whether a user is allowed to print at printing device 104. Private domains 120 and 130 can operate over the cloud. Public policy server 112 may enforce the rules of the policy but management of the policy is still at a private server. Public policy server 112 also needs to distinguish between the private servers and private domains. Thus, if a user is outside the private network for a private domain, public policy server 112 will find the correct private domain to connect. That private domain will validate the user and access or use of the print job.

FIG. 2 illustrates a block diagram of components of printing device 104 used in conjunction with system 100 according to the disclosed embodiments. The architecture shown in FIG. 2 may apply to any multi-functional printer or image forming apparatus that scans documents to perform other functions, such as printing, storing, copying, and the like. As disclosed above, printing device 104 may send and receive data from public domain 110 and private domains 120 and 130.

Printing device 104 includes a computing platform 201 that performs operations to support these functions. Computing platform 201 includes a computer processing unit (CPU) 202, an image forming unit 204, a memory unit 206, and a network communication interface 210. Other components may be included but are not shown for brevity. Printing device 104, using computing platform 201, may be configured to perform various operations, such as scanning, copying, printing, receiving or sending a facsimile, or document processing. As such, printing 104 may be a printing device or a multi-function peripheral including a scanner, and one or more functions of a copier, a facsimile device, and a printer. To provide these functions, printing device 104 includes printer components 220 to perform printing operations, copier components 222 to perform copying operations, scanner components 224 to perform scanning operations, and facsimile components 226 to receive and send facsimile documents. CPU 202 may issue instructions to these components to perform the desired operations.

Printing device 104 also includes a finisher 211 and one or more paper cassettes 212. Finisher 211 includes rotatable downstream rollers to move papers with an image formed surface after the desired operation to a tray. Finisher 211 also may perform additional actions, such as sorting the finished papers, binding sheets of papers with staples, doubling, creasing, punching holes, folding, and the like. Paper cassettes 212 supply paper to image the various components 220, 222, 224, and 226 to create the image formed surfaces on the papers. Paper cassettes 212 may include papers having various sizes, colors, composition, and the like. Paper cassettes 212 may be removed to refill as needed.

Document processor input feeder tray 230 may be the physical components of printing device 104 to receive papers and documents to be processed. A document is placed on or in document processor input feeder tray 230, which moves the document to other components within printing device 104. The movement of the document from document processor input feeder tray 230 may be controlled by the instructions input by the user. For example, the document may move to a scanner flatbed for scanning operations. Thus, document processor input feeder tray 230 provides the document to scanner components 220.

As shown in FIG. 2, document processor input feeder tray 230 may interact with engine firmware 106 to perform the desired operations.

Memory unit 206 includes memory storage locations 214 to store instructions 215. Instructions 215 are executable on CPU 202 or other processors associated with printing device 104, such as any processors within components 220, 222, 224, or 226. Memory unit 206 also may store information for various programs and applications, as well as data specific to printing device 104. For example, a storage location 214 may include data for running an operating system executed by computing platform 201 to support the components within printing device 104. According to the disclosed embodiments, memory unit 206 may store the tokens and codes used in performing the authentication operations for printing device 104.

Memory unit 206 may comprise volatile and non-volatile memory. Volatile memory may include random access memory (RAM). Examples of non-volatile memory may include read-only memory (ROM), flash memory, electrically erasable programmable read-only memory (EEPROM), digital tape, a hard disk drive (HDD), or a solid-state drive (SSD). Memory unit 206 also includes any combination of readable or writable volatile memories or non-volatile memories, along with other possible memory devices.

Computing platform 201 may host one or more processors, such as CPU 202. These processors are capable of executing instructions 215 stored at one or more storage locations 214. By executing these instructions, the processors cause printing device 104 to perform various operations. The processors also may incorporate processing units for specific purposes, such as application-specific integrated circuits (ASICs) and field programmable gate arrays (FPGAs). Other processors may be included for executing operations particular to components 220, 222, 224, and 226. In other words, the particular processors may cause printing device 104 to act as a printer, copier, scanner, and a facsimile device.

Printing device 104 also includes an operations panel 208, which may be connected to computing platform 201. Operations panel 208 may include a display unit 216 and an input unit 217 for facilitating interaction with a user to provide commands to printing device 104. Display unit 216 may be any electronic video display, such as a liquid crystal display (LCD). Input unit 217 may include any combination of devices that allow users to input information into operations panel 208, such as buttons, a touch screen, a keyboard or keypad, switches, dials, and the like. Preferably, input unit 217 includes a touch-screen digitizer overlaid onto display unit 216 that senses touch to receive inputs from the user. By this manner, the user interacts with display unit 216. Using these components, one may enter an identification code 138 generated by mobile application 110 into printing device 104.

Printing device 104 also includes network communication processing unit 218. Network communication processing unit 218 may establish a network communication, such as a wireless or wired connection with one or more other image forming apparatuses and a server in an image forming system. CPU 202 may instruct network communication processing unit 218 to transmit or retrieve information over a network using network communication interface 210. As data is received at computing platform 201 over a network, network communication processing unit 218 decodes the incoming packets and delivers them to CPU 202. CPU 202 may act accordingly by causing operations to occur on printing device 104. CPU 202 also may retrieve information stored in memory unit 206, such as settings for printing device 104.

Printing device 104 also includes engine 106. Engine 106 may be a combination of hardware, firmware, or software components that act accordingly to accomplish a task. For example, engine 106 is comprised of the components and software to print a document. It may receive instructions from computing platform 201 after user input via operations panel 208. Alternatively, engine 106 may receive instructions from other attached or linked devices.

Engine 106 manages and operates the low-level mechanism of the printing device engine, such as hardware components that actuate placement of toner onto paper. Engine 106 may manage and coordinate the half-toner, toner cartridges, rollers, schedulers, storage, input/output operations, and the like. Raster image processor (RIP) firmware 290 that interprets the page description languages (PDLs) would transmit and send instructions down to the lower-level engine 106 for actual rendering of an image and application of the toner onto paper during operations on printing device 104.

FIG. 3 depicts a flow diagram 300 for implementing policy-based printing system 100 according to the disclosed embodiments. In disclosing the embodiments shown by flow diagram 300, reference may be made to elements shown in FIGS. 1-2 and 4A, 4B, and 5. Flow diagram 300 shows the operations between the various servers disclosed in FIG. 1 above. Flow diagram 300 also depicts the actions taken at the various servers. The private and public servers may perform additional operations and actions not shown herein. The operations may be executed over network 102. Further, flow diagram 300 shows the operations between public domain 110 and private domain 120. Thus, firewall 122 may exist between the public servers and the private servers. The same operations may be executed between public domain 110 and private domain 130.

The processes disclosed by flow diagram 300 seek to solve the problem of how to authenticate a user in one location, such as a convenience store with printing services, that he/she is within an organization that has a policy applicable to the user. Further, the policy is stored in a private domain not readily accessible from the printing device at the convenience store. The printing device is connected to a public network and may be part of a public domain, such as public domain 110. The disclosed embodiments enable the user and the organization to implement the policy, which is applicable to the private domain, within the public domain of the printing device located in the convenience store.

Operation 302 executes by private authentication server 124 sending an initialization request to public policy server 112. As disclosed above, private authentication server 124 is within private domain 120 and public policy server 112 is within public domain 110. To send the initialization request, an administrator enter information about public policy server 112. Such information may include server network address, location, server capabilities, and the like. Once the information is entered, private authentication server 124 generates a verification token 502 which verifies that public policy server 112 is acceptable to receive information and communicate with the private authentication server.

Operation 304 executes by returning acceptance of the initialization request and establishing a protocol connection 144 between private authentication server 124 and public policy server 112. Protocol connection 144 may stay established as long as public policy server has verification token 502. Verification token 502 may be stored on public policy server 112 and presented whenever verification is required by private authentication server 124. Protocol connection 144 provides a persistent connection between private authentication server 124 and public policy server 112 that allows the servers to send data at any time. Protocol connection 144 preferably may be known as a WebSocket connection, which provides a full-duplex communication channel over a single connection. Preferably, protocol connection 144 uses a secure protocol.

Operation 306 executes by providing a domain list 400 from private authentication server 124 to public policy server 112. This operation also may include providing the information about the private authentication server. Action 308 executes by setting domain list 400 at public policy server 112 to include domain information for private authentication server 124. Public policy server 112 may refer to domain list 400 whenever a user attempts to print from a private domain. Public policy server 112 may use information provided by the user to determine which domain to obtain policy 142. For example, public policy server 112 may be connected to more than one private domain. Domain list 400 determines which private domain applies to a user trying to print.

FIG. 4A depicts an example domain list according to the disclosed embodiments. Domain list 400 may be a file having fields for the private domains and the email domains associated with each domain. A user is identified as part of a domain using his/her email address. Public policy server 112 will compare the email provided by the user to determine which private domain to access. As shown in FIG. 4A, private domain 120 may be associated with two email domains 402 and 404. A user having an email domain with “@example1.com” or “@example 2.com” will have its policy and associated documents located on private domain 120. A user having an email domain 406 with “@company.com” will have its policy and associated documents located on private domain 130. Additional private domains may be served by public policy server 112. Private domain N will receive requests for policies of users having email domain 408 of “@firm.com” and private domain N+1 will receive requests for policies of users having email domain 410 of “@college.com.”

As can be seen, companies, firms, and colleges have an interest in keeping their network domains private. Further, these entities may wish to limit use of printing devices within public domains according to a policy. Domain list 400 also may include an entry for a public domain, such as public domain X. In some instances, a public domain also may include policies to limit capabilities of a user on a printing device 104. These policies, however, may not be within a private domain and available for retrieving through a public network connection. An email domain of “@website.com” may direct public policy server 112 to a public domain for the associated policy 142. Referring back to FIG. 3, operation 310 returns an acknowledgement to private authentication server 124 that domain list 400 has been set and protocol connection 144 exists with public policy server 112.

Operation 312 executes when a user wants to print a document at printing device 104 coupled to public policy server 112. Authentication information 504 is provided from public policy server 112 to private authentication server 124. In some embodiments, the user enters a username and password that is captured by public policy server 112. For example, the user may enter this information at printing device 104 which forwards it to public policy server 112. Alternatively, the user may connect to public policy server 112 through an application on a mobile device or the like to provide authentication information 504.

In other embodiments, the user may enter a code, such as a personal identification number (PIN), that retrieves this information to provide it to public policy server 112. Public policy server 112 receives the code and matches the user information when the code is provided. Other embodiments may use a graphical code or identification card having a number that provides this information. Operation 312 sends this authentication information 504, such as username, password and PIN, to private authentication server 124.

Action 314 executes by authenticating the user with authentication information 504. Thus, user information is not stored on public policy server 112. Authentication still occurs in private domain 120 behind firewall 122. If the user is authenticated, then action 314 also includes private authentication server 124 generating authentication token 506. Operation 316 executes by indicating that the user has been validated and providing authentication token 506 to public policy server 112. Public policy server 112 may assign authentication token 506 to the user. Using the PIN example, the entered PIN may be associated with authentication token 506.

Private authentication server 124 also may provide an email address or the email domain, such as email domains 402-412 shown in FIG. 4A, to public policy server 112 if this information is not already available. For example, it may be too cumbersome to enter email addresses at printing device 104. Further, the administrators of private domain 120 may not want valid email addresses being entered at printing device 104 on a public network or in a public place. Thus, no email address is provided to public policy server 112 from within public domain 110 but, instead, from private domain 120. Moreover, private authentication server 124 may provide only the domain and not the actual email address.

Once validated, public policy server 112 now retrieves a policy 142 from private policy server 128. Operation 318 executes by getting policy 142. The email domain is compared against domain list 400 to determine which private domain to query for the policy. In this example, user@example1.com is the email provided to public policy server 112. It compares the email to domain list 400 to determine the applicable policy is within private domain 120. Public policy server 112 sends determined domain 508, such as example1.com, along with authentication token 506 to private policy server 128 in operation 318. If the next user has an email domain of @company.com, then public policy server 112 determines that domain 508 is company.com and that the applicable policy is located in private domain 130.

Action 320 executes by identifying policy 142 as being applicable to the user based on domain 508. Authentication token 506 may be associated with the user and this information provided from private authentication server 124. Policy 142 may be a file having flags or other information to indicate what the user can do within a public network. For example, limitations may be set as to what type of printing can be done, the number of pages may be printed, and the like. FIG. 4B depicts a block diagram of an example policy for policy 142 according to the disclosed embodiments.

Policy 142 may include policy information 448. Policy information 448 may include a title of the policy, document information, and private domain information. Policy 142 includes data, such as flags, that indicates what can and cannot be performed in public domain 110. This data may be known as parameters in policy 142. Examples of parameters that limit printing operations are shown in FIG. 4B. Print parameter 449 may be set to indicate whether a user can even print outside private domain 120. Certain users may not be allowed to print in a public domain. Print parameter 449 may be set to limit these users to scanning documents only or other operations that do not allow access to any documents or information stored in private domain 120.

Color parameter 450 may indicate whether the user can do color printing in public domain 110. If no, then the user may be limited to only black and write printing. The user may be allowed to do color printing at printing devices in private domain 120 but not allowed to do so in a public domain setting.

Pages parameter 452 may set a limit on the number of pages that a user can print. The administrators of private domain 120 do not want unlimited printing to occur outside the private domain. Pages parameter 452 may limit the number of pages printed per day, week, month, hour, year, and the like. Alternatively, pages parameter 452 may cap the number of pages printed to have the user check with the administrators of public domain 120 to reset this parameter. Once the user hits a limit, he/she requests that the number of pages printed be reset to allow further operations. Costs parameter 454 may be similar to pages parameter 452 except to limit the amount of fees that the user may incur before printing is stopped. Costs parameter 454 helps prevent the user from running up large bills at a convenience store. It also may cap the amount of costs incurred on a periodic basis or as a total cost.

Security level parameter 456 may indicate that the user can only access documents from a job list provided from private job server 126 having a certain security or access level. Security level parameter 456 may help prevent accidental or intentional printing of sensitive documents at printing device 104. Further, the user may have access to sensitive documents when printing within private domain 120 but not so when printing using public domain 110. Policy 142 may limit exposure to such documents.

Location parameter 458 may indicate whether the user can print at certain locations. Policy 142 may place geographic or other limitations on where the user can print using a public domain. Location parameter 458 also may indicate the type of locations to allow printing operations. For example, the administrators of private domain 120 may not allow printing in a convenience store but may allow printing in a library. Device parameter 460 may act similar to location parameter 458 except limit printing on certain devices. For example, policy 142 may not allow printing on a printing device 104 that does not have legal sized paper capability or stores the data from the job file in a memory on the device. Device parameter 460 also may limit printing operations to known printing devices having a serial number or IP address.

Operation 322 executes by providing policy 142 to public policy server 112. Public policy server 112 may configure policy 142 to determine whether the user can print using public domain 110 and what limits on the printing operations may be enforced. Policy 142 may apply to all users of private domain 120. Alternatively, policy 142 may treat users differently. Some users may have unlimited printing privileges according to parameters 452 or 454 while others are prevented from exceeding a cap set forth by these parameters. Public policy server 112 configures the determinations using policy 142 accordingly.

Using the parameters within policy 142, operation 324 executes by getting a job list from private job server 126. Public policy server 112 may generate a job token 510. Job token 510 is presented to private job server 126 to obtain a job list 511 of print jobs available to the user. In some embodiments, job token 510 may include data that specifies what print jobs can be added to job list 511 based on the parameters set forth in policy 146. Job list 511 includes those print jobs that meet the specifications of policy 146. For example, color print jobs will not be included in job list 511 of policy 146 does not allow color printing for the user in a public domain. Action 326 executes by generating job list 511 in response to job token 510. Operation 322 executes by sending the print jobs in job list 511 to public policy server 112 from private job server 126.

The user then may select a print job from job list 511. The user may select from an interface provided on printing device 104 that is then communicated to public policy server 112. Alternatively, an application may execute on a device of the user that presents the job list and allows for selection from the list. The selection is sent to public policy server 112. Operation 330 executes by sending a command to private job server 126 to prepare a selected print job along with a uniform resource locator (URL) address from public policy server 112. The URL address is one associate with public policy server 112 and accessible from public domain 110.

Action 332 executes by retrieving and preparing the data for the print job. Preferably, the data is binary data that represents the document for the print job. This may be shown as binary data 140 in FIGS. 1 and 5. Action 332 also may convert the data into a format compatible with printing device 104. For example, the document may include data that calls for printing on a legal sized paper while printing device 104 only prints using letter sized paper. The data sent from private job server 126 may be modified to fit onto a letter sized paper.

Operation 334 executes by uploading binary data 140 to the URL address provided in operation 330. Thus, private job server 126 puts the data for the print job outside private domain 120 for the first time at this point. The URL address may be valid for only a specified period of time, such as two hours, one day, a week, and the like. After that point, the URL address may expire. The URL address to download binary data 140 for the print job is provided to public file server 114.

Public policy server 112 now retrieves binary data 140 and sends the data to printing device 104. Before that occurs, however, the disclosed embodiments may confirm whether the user has enough funds to pay for processing and completing the print job. Operation 336 executes by generating a confirmation token 514 at public policy server 112 once it is confirmed that the user or user's account has enough money to cover expenses to print. Public policy server 112 may compare the funds available to the cost to complete the print job. If there are enough funds, then confirmation token 514 is generated and sent to public file server 114. If not, then the user may be alerted to add more funds to his/her account.

Action 338 executes by obtaining uploaded binary data 140 from the URL address. Public file server 114 may send a call to the URL address which then sends binary data 140 to the public file server. Public file server 114 may store binary data 140 until confirmation token 514 is received. If a confirmation token 514 is not received within a specified time frame, then binary data 140 may be deleted from public file server 114. This feature prevents print jobs from private domain 120 from being stored indefinitely in public domain 110. Other factors may be used to determine when to delete any stored files of binary data.

Operation 340 executes by sending binary data 140 for the print job from public file server 114 to public policy server 112. Operation 342 executes by sending binary data 140 from public policy server 112 to printing device 104. Printing device 104 may process the print job accordingly. The user's account for printing on public domain 110 may be charged accordingly as well. In some embodiments, public file server 114 may send binary data 140 to printing device 104.

The disclosed embodiments allow a private domain, or network, to print to a public domain using a policy applicable to the public domain. Internal policies to the private domain are not material to printing in the public domain. Further, job data is kept private as long as possible. The data for the print job is provided to the public domain when requested by the user and approved according to the policy. This feature allows the user to print anywhere. The print job is not automatically sent outside the private domain or from the private servers until printing actually occurs. The disclosed embodiments provide greater flexibility for companies and users to access documents in a secure, private location and use devices and resources in a public setting.

FIG. 6 illustrates a flowchart 600 for printing at printing device 104 within policy-based printing system 100 according to the disclosed embodiments. Flowchart 600 may refer back to elements disclosed in FIGS. 1-5 for illustrative purposes. The embodiments disclosed by flowchart 600, however, are not limited to the features disclosed in FIGS. 1-5. Further, flowchart 600 may compliment the embodiments disclosed by flow diagram 300.

Step 602 executes by establishing a protocol connection 144 between private authentication server 124 and public policy server 112. The protocol connection allows communication between the servers, one in private domain 120 and another one in public domain 110. Step 604 executes by providing a domain list 146 from private authentication server 124 to public policy server 112. Domain list 146 may include applicable private domains and associated email domains that are accessible by public policy server 112. Step 606 executes by entering user data 504 within public network 110 and providing the data to public policy server 112. Step 608 executes by sending user data 504 to private authentication server 124.

Step 610 executes by validating the user at private authentication server 124. Private authentication server 124 checks the provided user data 504 against its stored authentication records for the user. If the user is validated, then step 612 executes by generating authentication token 506. Step 614 executes by receiving authentication token 506 at public policy server 112. Step 616 executes by determining the applicable private domain for the user according to domain list 146. Preferably, public policy server 112 uses the email address for the user to determine which private domain to access for the policy for the user.

Step 618 executes by retrieving policy 142 from private policy server 128 based on the receipt of authentication token 506 and domain 508 from public policy server 112. Private policy server 128 is identified according to the applicable domain 508 and queried by public policy server 112. Once verified, private policy server 128 sends policy 142 to public policy server 112.

Step 620 executes by determining the parameters for policy 142. This process is disclosed above. As shown in FIG. 4B, policy 142 may include parameters that outline what printing options are available to the user. Step 622 executes by applying the parameters to configure public policy server 112 to determine what print jobs or operations are available to the user in public domain 110.

Step 624 executes by determining whether the user is allowed to access printing device 104 using public domain 110 according to the policy. Further, step 624 determines what print jobs are available to the user according to policy 142. The determination also may include reviewing policy 142 for allowing other operations on printing device 104 such as scanning, editing, faxing, and the like. If no, then step 626 executes by sending a message to the user or public policy server 112 that the operation on printing device 104 is not allowed.

If step 624 is yes, then step 628 executes by retrieving the print job from private job server 126. A job list 511 may be provided. The print job is selected from job list 511. Job token 510 is generated by public policy server 112. Public policy server 112 sends job token 510 to private job server 126 to obtain job list 511. Upon selection of the print job, private job server 126 uploads binary data 140 for the print job to a location accessible by public file server 114. Step 630 executes by confirming access to binary data 140 for the print job by checking to see if the user has enough money to pay for using printing device 104. Other restrictions also may be checked, such as time of day, location, and the like, to confirm whether the print job should be released to printing device 104.

Step 632 executes by sending binary data 140 to printing device 104 upon confirmation in step 630. Public policy server 112 generates a confirmation token 514 to confirm that the user is allowed to print. Public policy server 112 may send confirmation token 514 to public file server 114. Upon receipt of the confirmation token, public file server 114 may forward binary data 140 for the print job to public policy server 112, which provides the data file to printing device 104.

FIG. 7 illustrates a flowchart 700 for implementing a policy-based printing system 100 in a public domain 110 according to the disclosed embodiments. Flowchart 700 may refer back to elements disclosed in FIGS. 1-5 for illustrative purposes. The embodiments disclosed by flowchart 700, however, are not limited to the features disclosed in FIGS. 1-5.

Further, flowchart 700 may compliment the embodiments disclosed by flow diagram 300.

As disclosed above, public policy server 112 may interact with a plurality of private domains. Public policy server 112 may retrieve and implement more than one policy for printing or processing print jobs in public domain 110. In some embodiments, public policy server 112 may implement policies for a plurality of public domains as well. Further, a plurality of printing devices may be connected to public policy server 112. Flowchart 700 discloses some embodiments that have public policy server 112 interacting with more than one private domain.

Step 702 executes by validating users within public domain 110 at private authentication server 124. As disclosed above, a protocol connection may be established between public policy server 112 and private authentication server 124 to exchange user information to perform the validation.

Step 704 executes by determining a private policy server for each user according to a domain for the user at public policy server 112. The domains for each user are private domains. Preferably, the email domain for each user indicates the applicable private domain for that user. With two or more users, different email domains may indicate more than one private domain. Step 706 executes by retrieving a policy 142 for each user according to the respective domain from private policy server 128.

Step 708 executes by determining the parameters for each policy 142. All of the policies are received at public policy server 112. Public policy server 112 configures the treatment of printing requests for each private domain according to the corresponding policy. The policy sets forth the parameters for printing from the private domain via the public domain. For example, the parameters for one policy may only allow 100 pages to be printed per user a month from private domain 120 while the parameters for another policy may only allow 20 pages to be printed per user from private domain 130. Public policy server 112 is configured accordingly.

Step 710 executes by determining whether the user is allowed to print according to the applicable policy. If no, then step 712 executes by sending an alert to public policy server 112 or to the user. No printing operations using public domain 110 are allowed. If yes, then step 714 executes by receiving a job list according to the applicable policy from private job server 126. Step 716 executes by making the print jobs in the job list available to the user. Step 718 executes by selecting a print job from the job list. Binary data 140 for the selected print job is retrieved from private job server 126 and made available to public file server 114.

Step 720 executes by confirming whether the print job may be sent to printing device 104. Public policy server 112 confirms that the user has enough funds or credits to perform the request task on printing device 104. If yes, then step 722 executes by sending the print job as binary data 140 to printing device 104. If no, then step 724 executes by denying the print job. The user may be prompted to provide additional funds or credits to perform the requested task.

FIG. 8 depicts a flowchart 800 for implementing a policy-based printing system 100 using tokens according to the disclosed embodiments. Flowchart 800 may refer back to elements disclosed in FIGS. 1-5 for illustrative purposes. The embodiments disclosed by flowchart 800, however, are not limited to the features disclosed in FIGS. 1-5. Further, flowchart 800 may compliment the embodiments disclosed by flow diagram 300.

Step 802 executes by generating authentication token 506 at private authentication server 124. This step occurs once private authentication server 124 validates a user attempting to print using public domain 110. Public policy server 112 sends user information 504 including an email address, username, password, or PIN to private authentication server 124. Private authentication server 124, being in private domain 120, may securely store this information for the user. The secure user information is not made available in public domain 110. Authentication token 506 indicates that the user may access private domain 120. Step 804 executes by sending authentication token 506 to public policy server 112.

Step 806 executes by sending authentication token 506 and domain 508 to private policy server 128. Public policy server 112 sends authentication token 506 and domain 508 after the domain is determined using domain list 146. An email address may indicate an email domain that is used as domain 508. Domain 508 indicates which private domain to access for the applicable policy. For example, referring to FIG. 4A, an email of user@example1.com will indicate private domain 120. Public policy server 112 attaches authentication token 506 to domain 508 and sends the request for the policy for the user.

Step 808 executes by retrieving policy 142 from private policy server 128. Authentication token 506 confirms that the user corresponds to the policy. Authentication token 506 may include data provided by private authentication server 124 that identifies the user as able to use private domain 120 and, therefore, policy 142 for the private domain should be used in printing on public domain 110. Private policy server 128 sends policy 142 to public policy server 112. Public policy server 112 then configures itself to apply the parameters of the policy to using public domain for the user.

Step 810 executes by generating job token 510 at public policy server 112 after applying the parameters of policy 142. The parameters may detail what the user can do using public domain 110. These parameters may not necessarily correspond to what the user can do using private domain 120. Limitations are placed on the user on how he/she can use printing device 104. Job token 510 may reflect the parameters to compile the job list of print jobs available to the user according to policy 142.

Step 812 executes by sending job token 510 to private job server 126. Private job server 126 may store the print jobs available to the user or to users in private domain 120. In some embodiments, a plurality of print jobs may be available such that a job list 511 is generated based on the parameters for the user in using public domain 110. Job token 510 may be used in generating job list 511 in that it includes information to select the appropriate print jobs to include in the print job list.

Step 814 executes by providing print job list 511 to public policy server 112. The user may select a print job from print job list 511. Alternatively, the desired print job may already be selected such that public policy server 112 receives data for the selection, such as from an application on a mobile device, that corresponds to the print job in job list 511. Public policy server 112 then requests the print job data from private job server 126. Step 816 executes by sending job binary data 140 for the selected print job from private job server 126 to public file server 114.

Step 818 executes by confirming whether the user may print or process the print job at printing device 104. For example, public policy server 112 may confirm that the user has enough funds in an account to pay for printing on printing device 104. If step 818 is no, then step 820 executes by sending an alert to the user or to public policy server 112 that printing operations are to be stopped until the condition is met. Using the above example, the user may be asked to provide additional funds to his/her account to print the document.

If step 818 is yes, then step 822 executes by generating confirmation token 514 by public policy server 112. Confirmation token 514 indicates that the processing of binary data 140 at printing device 104 may proceed. Step 824 executes by sending confirmation token 514 to public file server 114 to obtain binary data 140, which is stored thereon. Public file server 114 may send binary data 140 to public policy server 112 upon receipt of confirmation token 514.

Step 826 executes by providing binary data 140 to printing device 104. Public policy server 112 may send binary data 140 once a connection is established with printing device 104. Public policy server 112 may have to wait until printing device 104 is available before forwarding binary data 140. Thus, the data from private job server 126 is not made available on printing device 104 until the operations are ready to commence. Although the current embodiments discuss printing on printing device 104, other operations also may occur, such as scanning, editing, faxing, and the like.

FIG. 9 depicts a flowchart 900 for selecting a plurality of print jobs from a plurality of private domains 120 and 130 for printing in public domain 110 according to the disclosed embodiments. Flowchart 900 may refer back to elements disclosed in FIGS. 1-5 for illustrative purposes. The embodiments disclosed by flowchart 900, however, are not limited to the features disclosed in FIGS. 1-5. Further, flowchart 900 may compliment the embodiments disclosed by flow diagram 300.

As disclosed above, different policies apply to different to users and prints jobs from different private domains. One private domain may not allow color printing while another private domain may not allow unlimited printing. Thus, public policy server 112 configures itself to resolve the different requirements set forth in a plurality of policies from various private policy servers. Further, public policy server 112 may manage different job lists and print jobs from the plurality of private domains. Alternatively, a private domain may have different domains related to it, such as example1.com and example 2.com for private domain 120 shown in FIG. 4A. Different policies may come from a single private policy server.

Step 902 executes by generating verification token 502 at private authentication server 124. Private authentication server 124 receives information about public policy server 112 in order to establish a protocol connection. Verification token 502 helps to establish a connection between private authentication server 124 and public policy server 112. Private authentication server 134 also may generate a verification token 502 to establish protocol connection to public policy server 112.

Step 904 executes by sending verification token 502 to public policy server 112. Step 906 executes by storing verification token 502 at public policy server 112. As long as public policy server 112 can present verification token 502 when requested or when submitting a print request for a user, the connection is established with private authentication server 124. Step 908 executes by providing domain list 146 from private authentication server 124 to public policy server 112. Domain list 146 may include information pertaining to a plurality of domains for a plurality of private domains, as disclosed by FIG. 4A.

Step 910 executes by generating a first authentication token 506. Step 912 executes by generating a second authentication token 506. The first authentication token may be generated in response to a first user providing user information at public policy server 112. The second authentication token may be generated in response to a second user providing user information at public policy server 112. Public policy server 112 may access the appropriate private authentication server to validate the user information for each user. In some embodiments, private authentication server 124 may validate both users and generate both authentication tokens. Alternatively, private authentication server 124 may generate the first authentication token while private authentication server 134 may generate the second authentication token. Public policy server 112 may have instructions when to use the different private authentication servers.

Step 914 executes by sending the first authentication token and a first domain to a first private policy server. Step 916 executes by sending the second authentication token and a second domain to a second policy server. Public policy server 112 determines which private domain is applicable to each user. The determination of the private domain may be based on the email address for each user. In some embodiments, public policy server 112 may send this data to a single private policy server, which stores different policies for different domains that use a single private domain. Alternatively, the authentication tokens and domains may be sent to separate private policy servers. For example, the first authentication token and first domain are sent to a first private policy server, such as private policy server 128. The second authentication token and the second domain are sent to a second private policy server, such as private policy server 138.

Flowchart 900 proceeds to steps A1 and A2 for steps 914 and 916, respectively. Steps A1 and A2 then proceed to steps 918 and 920, respectively. Step 918 executes by retrieving a first policy, such as policy 142, in response to the first authentication token and the first domain. Step 920 executes by retrieving a second policy, such as policy 142, in response to the second authentication token and the second domain. In some embodiments, the first policy is stored on private policy server 128 and the second policy is stored on private policy server 138. Alternatively, both policies may be stored on private policy server 128 or 138. The first policy may apply to the first user and the second policy may apply to the second user.

Step 922 executes by receiving the first and second policies at public policy server 112. Step 924 executes by determining access to a first print job according to the first policy and access to a second print job according to the second policy. Public policy server 112 may configure the parameters of each policy to determine what type of print jobs may be made available to each user. For example, the first print job may not be available to the second user according to the second policy. The determination of access may relate to what print jobs are available to the users over public domain 110.

Step 926 executes by generating first and second job tokens, such as job token 510, based on the first and second policies at public policy server 112. A first job token is generated for the first policy and a second job token for the second policy. In some embodiments, the first job token may be sent to private job server 126 and the second job token may be sent to private job server 136. The different private job servers are in separate private domains. Alternatively, the job tokens may be sent to private job server 126 or 136.

Step 928 executes by retrieving a first job list, such as job list 511, based on the first policy and the received first job token and retrieving the second job list, such as job list 511, based on the second policy and the received second job token. The applicable private job server or servers provide the job lists to public policy server 112. The first user may select a first print job from the first print job list. The second user may select a second print job from the second print job list. These requests are communicated back to the application private job server or servers. The binary data for the first and second print jobs are sent to public file server 114.

Step 930 executes by generating confirmation tokens, such as confirmation token 514, at public policy server 112 to indicate that the print jobs may be processed at printing device 104. Public policy server 112 may confirm that each user has enough funds in his/her account to perform operations on printing device 104, as disclosed above. A first confirmation token for the first print job is presented to public file server 114. A second confirmation token for the second print job is presented to public file server 114. Public file server 114 provides the binary data for each print job to public policy server 112. Step 932 executes by sending the binary data for the first and second print jobs to printing device 104.

In some embodiments, it may be desired to not provide the policy to the public domain, either in a public domain server or the printing device. The policy could include details that are sent to many components within the system. Some servers and devices may not be able to implement the policy effectively. A policy may be a complex concept.

Whenever policy data arrive at the device, the data may need to be parsed correctly and applied correctly when a print job is sent to the device. These operations may impose a heavy burden on the development and maintenance of the device. Preferably, the printing system would like the printing device, for example, to focus on what it does, such as printing, scanning, or copying.

FIG. 10 illustrates a policy-based system 1000 to implement policy-based printing using a private server 1002 according to the disclosed embodiments. System 1000 may reduce development and maintenance responsibilities in multiple components in the system and provide additional security with an advanced policy. In some embodiments, a private server at the corporate office, or private domain, has the policy set by an administrator. The policy changes frequently and becomes more complex with each evolution of software within the printing system or on the devices.

On the private server, a ledger may exist that records all the actions performed by all end user who are printing, copying, scanning, and the like within system 1000. The users may utilize printing devices and servers in a public domain such that they perform actions outside the normal corporate environment. A public server may serve as a gateway to the private domain. It may have open websocket bi-directional communication with the private server, as disclosed above. The printing device is connected to the public network and also is connected to the public server to whether it can do a simple action on behalf of the user in processing a document.

Within the disclosed printing system, the user may use allowed printing or access to documents in each policy period in an uneven manner. The user does not use the services of the printing devices the same way or amount every period. One period may not use the allotted number of pages to be printed while another period may exceed the limit placed on the user by the policy. Further, usage from a future period may be used and applied to the current period in order to allow the user to print documents. The disclosed embodiments address this imbalance to improve the user experience and provide better usage strategies for the user and the business.

FIG. 10 shows a policy-based system 1000 having a private server 1002, a public server 1004, a printing device 1006, and a user device 1008. These components of the system may be disclosed above with regard to FIGS. 1-9. In system 1000, private server 1002 may refer to any of the servers in the private domain, such as private authentication server 124, private job server 126, and private policy server 128 of private domain 120 shown in FIG. 1. Private server 1002 may be used in system 1000 to mean any server or group of servers in a private domain, as disclosed above. Private server 1002 may be separated from servers and printing devices in public domains by firewall 1011. Private server 1002 also stores and applies policy 1010. Policy 1010 may correspond to policy 142 disclosed above.

Public server 1004 may refer to any of the servers in the public domain, such as public file server 114 and public policy server 112 of public domain 110 shown in FIG. 1. Public server 1004 may be accessible by a plurality of printing devices, including printing device 1006. In the public domain, public server 1004 may manage print jobs going to various printing devices. It also may include a connection to private server 1002, which has been verified and authenticated according the processes disclosed above. For example, a websocket connection 1005 may exist between private server 1002 and public server 1004.

Printing device 1006 may receive documents from public server 1004 as well as other sources to print, modify, and the like. The features of printing devices according to the disclosed embodiments are disclosed above. Printing device 1006 may include device identification 1018 that indicates a unique identifier within system 1000. In some embodiments, device identification 1018 may be a number, alphanumeric characters, or a combination thereof. Public server 1004 may send documents and files to printing device 1006 based on device identification 1018.

Mobile device 1008 may be a mobile device, tablet, laptop, and the like. Mobile device 1008 may move between the private domain and the public domain, as separated by firewall 1011. It also may access private server 1002 as well as public server 1004. A user may send and receive data from the servers at mobile device 1008. Mobile device 1008 also may send instructions 1014 to printing device 1006 to print, copy, scan, and the like stored documents from private server 1002.

Private server 1002 may upload document 1012. Document 1012 may be similar to the print jobs disclosed above. Document 1012 includes data and information that is transmitted to devices within the private domain. The user of user device 1008 may upload document 1012 within the private domain. Document 1012, however, may be processed and printed at devices outside the public domain and not necessarily at devices connected to private server 1002. Policy 1010 also may be used to determine how and if document 1012 is used within system 1000 outside the private domain.

The user may authenticate mobile device 1008 to public server 1004 according to the disclosed embodiments. For example, mobile device 1008 may provide verification data, such as a user/account name and password, to verify the user to public server 1004. This process may be disclosed above with regard to verification between public policy server 112 and private authentication server 124. Alternatively, the verification data may be a token used by user device to authenticate the user in a public domain. Upon authentication, websocket connection 1005 may be established to allow open bi-directional communication between private server 1002 and public server 1004.

In some embodiments, printing device 1006 receives instructions 1014 from mobile device 1008 to process document 1012. An electronic copy of document 1012 may be sent to printing device 1006 to process and print, copy, scan, and the like. The user also may modify the electronic copy. In summary, a document stored on private server 1002 is made available on a public device.

Before receiving document 1012, printing device 1006 in conjunction with public server 1004 and private server 1002 may determine whether any action on behalf of the user is allowed at the printing device. An action by printing device 1006 is a simple operation of print, copy, scan, and the like. It may be measured in the smallest scale possible, such as a single page at a time. Thus, printing device 1006 may send request 1016 to public server 1004, which is then forwarded to private server 1002. Printing device 1006 does not do any analysis of policy 1010. Private server 1002 applies policy 1010 to determine whether printing operations allowed on behalf of the user at printing device 1006, as disclosed above by FIG. 3.

Public server 1004 receives request 1016 pertaining to the user instructions to printing device 1006 to process document 1012. Public server 1004 may forward request 1016 without further processing. In other embodiments, public server 1004 may determine whether request 1016 is acceptable to private server 1002. Public server 1004 also may perform tasks on behalf of private server 1002, such as store documents to be sent to the printing devices. Public server 1004 also may track print jobs to completion. Upon receipt of responses from private server 1002, public server 1004 may forward document 1012 or provide further instructions to printing device 1006.

Private server 1002 receives request 1016 from public server 1004 via websocket connection 1005. If no websocket connection exists, then private server 1002 may not receive the request and public server 1004 responds to printing device 1006 with an alert that printing, copying, scanning, and the like for request 1016 is denied. Upon receipt of request 1016, private server 1002 analyzes policy 1010 to determine whether the action is allowed for the user on printing device 1006. Private server 1002 also compiles or accesses ledger 1003 to determine if the action is allowed. Ledger 1003 may be a record or file of all fine grained action within system 1000 that provides the status of the account for the user. For example, ledger 1003 may indicate how many pages that the user has printed in the policy-set period, costs incurred, and other statistics of actions limited by policy 1010.

Update 1020 also may be received at private server 1002 that impact policy 1010 and ledger 1003. Update 1020 may change the parameters of interest to policy 1010 or provide temporary adjustments to the policy. For example, the user may exceed his/her printing page limit by a specified number of pages for a 24 hour period. The user is attending an important off-site meeting or conference that would provide a good reason to exceed the daily printing limit. Update 1020, however, is not meant to be permanent. In the disclosed embodiments, update 1020 may be implemented in a more efficient manner by keeping policy 1010 at private server 1002 as opposed to having it stored on public server 1004. Private server 1002 does not need to update policies in the public domain or on different devices because all policy analysis and determinations may be performed at the private server. In some embodiments, update 1020 may modify policy 1010 to allow unused usage from a previous period or borrow usage from a future period for a current period.

Depending on the results of the determination, private server 1002 sends response 1022 to public server 1004. Response 1022 may include a copy of document 1012 for printing. Document 1012 may be sent as a data file intended to reproduce the document at printing device 1006. Response 1022 may include more than one response, but is shown as a single response for brevity. Public server 1004 may analyze the response to ensure it is appropriate. Public server 1004 forwards response 1022 to printing device 1006, which acts accordingly. In some embodiments, public server 1004 also may send response 1022 or a message associated thereto to user device 1008. The response sent to mobile device 1008 also may include statistics or information regarding the status of the user's account based on ledger 1003 and policy 1010.

System 1000 shows mobile device 1008 sending instructions 1014 to printing device 1006. In some embodiments, the user may interact directly with printing device 1006 to process document 1012 thereon. Use of a mobile device 1008 is not required to print, copy, or scan a document at printing device 1006 or within the public domain. Further, mobile device 1008 may generate request 1016 to print document 1012 at printing device 1006. The request is forwarded to private server 1002 through public server 1004. Mobile device 1008 also may receive a response 1022 to indicate the document is being printed or may receive the document itself, which is then provided to printing device 1006.

FIG. 11 depicts a policy-based printing system 1000 implementing split printing between two printing devices according to the disclosed embodiments. FIG. 12 depicts a block diagram of data within public server 1004 for split printing according to the disclosed embodiments. At times in a private to public print job, the printing device runs out of paper or goes off-line before the print job is finished. The print job is allowed according to the policy and private server but not completed. To continue printing, the user must move to another printing device and, possibly, even another location. The private server using the ledger and the policy may indicate that the user cannot print the document again at the second printing device. Further, the user does not want to print the whole document, but only the remaining pages. This action avoids unnecessary printing and reduces costs.

The user also does not want to go through the actions disclosed above of resubmitting the request and await approval for another print job. Thus, the disclosed embodiments create another print job with the remaining page range. The authenticated print policy is attached to the remaining print job so the disclosed embodiments is not required to reacquire authentication from the private server. The disclosed embodiments allow the user to continue printing at any public server accessible by the public server.

Referring to FIG. 11, system 1000 is with data and information used to facilitate the split printing processes. The features shown in FIG. 10 also are included here but not shown for brevity. System 1000 also includes another printing device 1102. Printing device 1102 is connected to public server 1004 and includes its own device identification 1104. Device identification 1104 indicates that printing device 1102 is a separate device within system 1000 from other printing devices, such as printing device 1006 having device identification 1018. Printing device 1102 may generate print requests and execute print jobs.

Mobile device 1106 is shown having mobile application 1106. Mobile application 1106 may facilitate printing operations within system 1000. Mobile application 1106 may receive and send data to public server 1004. It also may keep track of print jobs for the user of mobile device 1108. In some embodiments, mobile application 1106 may store personal identification numbers (PINs) used within system 1000. The user may access mobile application 1106 to retrieve the PINs to use within system 1000. As disclosed below, the PINs may be codes that are entered or provided to devices within system 1000. The PINs may be numbers, alphanumeric, and graphical codes displayed on mobile device 1106 using mobile application 1106. For illustrative purposes, the PINs disclosed below may be treated as a sequence of numbers.

Private server 1002 may generate a corporate PIN 1108 when document 1012 is uploaded by the user. Corporate PIN 1108 is associated with document 1012 in that private server 1002 will retrieve document 1012 and policy 1010 when the corporate PIN is received from public server 1004. The user also may use corporate PIN 1108 in the private domain to print from printing devices connected directly to private server 1002. In other words, corporate PIN 1108 may be used to retrieve document 1012 from any location of the user. Corporate PIN 1108 may be stored by mobile application 1106.

When the user wants to print document 1012 in the public domain, such as using printing device 1006, mobile application 1106 may submit corporate PIN 1108 to public server 1004. The user may authenticate using public server 1004 using authentication information, as disclosed above. Public server 1004 determines that the user of mobile device 1008 is allowed to print using private server 1002. The user enters corporate PIN 1108 generated from private server 1002 to “print” to public server 1004. Referring to FIG. 12, an entry is made on public server 1004 associated with corporate PIN 1108 for a user account 1200. User authentication information 1202 may be used to generate a field for user account 1200 in memory of public server 1004 that stores associated corporate PINs to the user. Preferably, user authentication information 1202 also includes an address for mobile device 1008 for exchanging data with mobile application 1106.

Public server 1004 submits corporate PIN 1108 to private server 1002. Private server 1002 verifies corporate PIN 1108. In a sense, the submission of corporate PIN 1108 acts as a request 1016 disclosed above to print a document. Private server 1002 applies policy 1010 to determine whether to allow the print job to proceed. If denied, then an alert may be sent to the user via mobile device 1008. If allowed, then document 1012 is retrieved and copied from private server 1002 to public server 1004. Moreover, policy 1010 may be attached to the corporate PIN and provided to public server 1004.

In response to receiving these files, public server 1004 generates public PIN 1110. Public PIN 1110 is associated with corporate PIN 1108. Referring to FIG. 12, public PIN 1110 may be stored with corporate PIN 1108 in user account 1200. Further, policy 1010 will be attached to public PIN 1110 so there is no need to apply the policy again at the time of printing. In some embodiments, data 1204 is associated with the entry for public PIN 1110 that indicates the print job associated with the PIN has been allowed by policy 1010. Data 1204 may be a flag or code that indicates to public server 1004 that the print job may proceed when public PIN 1110 is received from a printing device. Data 1204 may be used if policy 1010 is not available or stored on public server 1004. In some instances, private server 1002 may not allow policy 1010 to be used outside the private domain.

Public PIN 1110 is provided to the user. Mobile application 1106 may receive public PIN 1110 and associate it with corporate PIN 1108 and document 1012. When the user selects document 1012 to print, he/she may be provided public PIN 1110 to enter onto the appropriate printing device. As corporate PIN 1108 was used to determine whether the print job is allowed by policy 1010, public PIN 1110 does not need to go through such an analysis. Public server 1004 may associate public PIN 1110 to corporate PIN 1108. The user enters public PIN 1110 into printing device 1006. Document 1012 is retrieved by public server 1004 and sent to printing device 1006. Preferably, document 1012 is completely printed out by printing device 1006.

In some instances, however, printing operations may be stopped before document 1012 is completely printed. For example, printing device 1006 may run out of paper. The user does not have the authority or ability to place paper into printing device 1006. Printing operations need to continue elsewhere, perhaps even a different location. Referring to FIG. 12, transaction 1206 is received at public server 1004 that indicates operations are completed but document 1012 is not totally printed out.

Transaction 1206 also may include what pages or items have been printed and what is remaining. Referring to FIG. 11, document 1012A may represent the portion of document 1012 is printed by printing device 1006. The portion of document 1012A may be noted by user account 1200 using stop information 1212 in transaction 1206. As shown in FIG. 12, stop information 1212 indicates how far in the printing operation proceeded for document 1012. The remaining, unprinted pages may be shown by document 1012B. The printed pages are accounted for on public server 1004 in document 1012. Private server 1002 may not be involved. Completion data 1208 may indicate that public PIN 1110 is used and no longer available. In other words, the user may not enter public PIN 1110 on another printing device.

In response to transaction 1206, public server 1004 generates public PIN 1112, or a second public PIN, for the print job. Public PIN 1112 also includes a new code as well as the remaining page range to be printed in document 1012, shown as document 1012B. The remaining page information may be stored on public server 1004. Public PIN 1112 also is authenticated by policy 1010 at public server 1004. Public server 1004 does not need to send another request to private server 1002. As noted above, such a request would require adjustments to ledger 1003 and delays in determining whether the rest of document 1012 can be printed out. The disclosed embodiments remove this need by handling the split print operations at public server 1004.

Public server 1004 confirms the authenticated policy credentials for public PIN 1112 by associating the credentials for policy 1010 using corporate PIN 1108. It determines that document 1012 is already approved for printing and adds this information to public PIN 1112 to its entry for corporate PIN 1108 as data 1204, disclosed above. Public PIN 1112 may be sent to mobile application 1106 on mobile device 1008. The user then selects another printing device to print the remaining pages of document 1012.

Referring to FIG. 11, the user may enter public PIN 1112 into printing device 1102. Printing device 1102 is a different device than printing device 1006, as indicated by device identification 1104. Printing device 1102 may include a separate IP address in that mobile device 1008 transmits public PIN 1112 to commence printing operations. Printing device 1102 forwards public PIN 1112 to public server 1004 to retrieve the remaining pages, or document 1012B.

Public server 1004 receives and verifies public PIN 1112. Document 1012B is sent to printing device 1102. Because policy 1010 already authorized printing to document 1012B, there is no need to send a request to private server 1002. Printing device 1102 receives document 1012B and completes the printing of document 1012. The user, therefore, prints document 1012 between two or more printing devices without the need to reacquire policy 1010 from private server 1002.

In some embodiments, more than two public PINs may be issued during the printing of document 1012. Transaction 1214 is received from printing device 1102 that printing is complete. If printing is not complete, then public server may determine the remaining pages and generate another code for a public PIN, as disclosed above. Another entry may be made for corporate PIN 1108. If printing is complete, then public server 1004 may use transaction 1214 to generate statistics for private server 1002 about the print job so that ledger 1003 may be updated. Corporate PIN 1108 and any associated public PINs may be deleted from public server 1004. Mobile application 1106 also may delete any PINs received to complete the print job of document 1012.

FIG. 13 depicts a flowchart 1300 for printing using public server 1004 in a policy-based system 1000 according to the disclosed embodiments. Flowchart 1300 may refer to FIGS. 1-12 for illustrative purposes. The embodiments disclosed by flowchart 1300, however, are not limited by the features of FIGS. 1-12.

Step 1302 executes by uploading document 1012 to private server 1002. Document 1012 may be uploaded by the user. In some embodiments, mobile device 1008 may upload document 1012. Step 1304 executes by generating corporate PIN 1108 by private server 1002. Corporate PIN 1108 may be a code that corresponds to document 1012. When received at private server 1002, corporate PIN 1108 indicates that document 1012 is requested to be printed. If received within the private domain with private server 1002, then document 1012 may be printed to the device. If the device is outside the private domain, then policy 1010 is applied to determine whether document 1012 may be printed.

Step 1306 executes by sending corporate PIN 1108 to mobile application 1106 on mobile device 1008 of the user. Mobile application 1106 may store corporate PIN 1108 on mobile device 1008 and make it available when requested by the user. The user may select document 1012 to print and corporate PIN 1108 displayed on mobile device 1008. When using public devices, mobile application 1106 may not be able to provide corporate PIN 1108 to use on public printing devices, such as in a convenience store.

Step 1308 executes by receiving corporate PIN 1108 at public server 1004 from mobile application 1106. The user wishes to print document 1012. Mobile application 1106 sends corporate PIN 1108 to request approval to print document 1012. Public server 1004 may create an entry for corporate PIN 1108 for user account 1200. Public server 1004 then generates a request 1016 for document 1012. Request 1016 may include an actual request, as disclosed above, or may just include corporate PIN 1108. Public server 1004 sends the request to private server 1002 over connection 1005.

Step 1310 executes by associating corporate PIN 1108 with document 1012. Private server 1002 receives corporate PIN 1108 from public server 1004. Private server 1002 may verify that corporate PIN 1108 is acceptable. It then determines which document is associated with the code. Private server 1002 also notes that a policy applies to any printing of the document by the user. Thus, step 1310 also includes associating policy 1010 with corporate PIN 1108 in the sense that it is used in conjunction with document 1012.

Step 1312 executes by applying policy 1010 to determine whether to print document 1012. Public server 1004 may receive document 1012 before it is provided to a printing device. Thus, policy 1010 is applied to determine whether document 1012 is provided to public server 1004. An actual printing device is not considered at this point. The application of a policy to determine whether to print is disclosed in greater detail above.

Step 1314 executes by determining whether to allow the print job for document 1012 as requested by the user. If no, then step 1316 executes by sending an alert that printing is denied by private server 1002. The alert may be sent to mobile application 1106 to inform the user. An alert also may be sent to public server 1004 to deny further requests related to corporate PIN 1108. If step 1314 is yes, then step 1318 executes by copying document 1012 to public server 1004. The data files enclosing the information needed to print document 1012 is sent. The data is associated with corporate PIN 1108 at public server. For example, document 1012 may be stored at user account 1200 with corporate PIN 1108.

Step 1320 executes by generating public PIN 1110 by public server 1004 in response to document 1012. Public PIN 1110 also is associated with corporate PIN 1108 so that receipt of the public PIN at public server will identify document 1012 to print. Step 1322 executes by sending public PIN 1110 to mobile application 1106. Mobile application 1106 may alert the user that the public PIN is received. Public PIN 1110 may be displayed on mobile device 1008.

Step 1324 executes by receiving public PIN 1106 at printing device 1006. This step is disclosed in greater detail by FIG. 15. The user may enter the code for public PIN 1106 on operations panel 208 or other interface for the printing device. Printing device 1006 captures the characters for the code and generates a request based on the code. Alternatively, mobile application 1106 may send the code for public PIN 1106 to printing device 1006 over a network or with an electronic connection. The user does not enter information onto the printing device. Printing device 1006 may confirm the code and generate the request using the code.

Step 1326 executes by sending public PIN 1110 to public server 1004 from printing device 1006. Public server 1110 confirms receipt and verifies that public PIN 1110 is acceptable. Step 1328 executes by associating public PIN 1110 with corporate PIN 1108. Data for user account 1200 may be analyzed to identify document 1012 to print at printing device 1006 using the associated corporate PIN 1108. In other embodiments, public server 1004 may identify document 1012 using public PIN 1110.

Step 1330 executes by retrieving document 1012 stored on public server 1004. Public PIN 1110 does not need to be verified using policy 1010 at private server 1002 as this determination is made earlier using corporate PIN 1108. Public server 1004 in a sense includes policy 1010 being attached to public PIN 1110. Step 1332 executes by sending document 1012 to printing device 1006, as indicated by public PIN 1110.

FIG. 14 depicts a flowchart 1400 for performing split printing using public server 1004 and different printing devices 1006 and 1102 according to the disclosed embodiments. Flowchart 1400 may refer to FIGS. 1-13 for illustrative purposes. The embodiments disclosed by flowchart 1400, however, are not limited by the features of FIGS. 1-13.

Step 1402 executes by printing document 1012 at printing device 1006 based on the use of public PIN 1110, as disclosed in flowchart 1300. Step 1404 executes by stopping the print job for document 1012, as requested by the user of mobile application 1106. Step 1406 executes by determining whether the print job is complete. If yes, then flowchart 1400 proceeds to step 1426.

In some instances, printing operations may be stopped at the printing device due to some condition. For example, the printing device may run out of paper or may include an error that needs to be addressed. A paper jam may occur that stops printing any more pages of the document. The printing device may go off-line for some reason. The user, however, may not be able to fix or resolve the problem or stoppage of printing operations. Further, it may be hours or longer before the issue with the printing device is resolved. The user, therefore, may need to move to another printing device to complete printing.

Thus, if step 1406 is no, then step 1408 executes by determining the unprinted portion of document 1012. In some embodiments, the unprinted portion may be pages. In other embodiments, it may be files not printed. Printing device 1006 captures this data. Step 1410 executes by sending transaction 1206 to public server 1004 with information about the unprinted portion of the print job. Transaction 1206 may indicate the number of pages printed and others remain unprinted.

Step 1412 executes by generating a public PIN 1112 for the remaining unprinted portion of document 1012. Public server 1004 notes that public PIN 1110 is already used and, therefore, not available to continue printing. Use of public PIN 1110 again also would cause the entire document to be sent to the new printing device, which may violate policy 1010. Thus, a new public PIN 1112 is generated without needing to apply policy 1010. Public server 1004 identifies the unprinted portion with corporate PIN 1108 that is approved by policy 1010. The approval is placed with public PIN 1112 to continue printing operations.

Step 1414 executes by sending public PIN 1112 to mobile application 1106 on mobile device 1008. The user may be notified and informed that he/she may continue printing at another printing device. The user moves to printing device 1102 for printing the rest of document 1012. Step 1416 executes by receiving public PIN 1112 at another printing device 1102. The different ways to provide a public PIN to a printing device are disclosed above and in greater detail by FIG. 15 below. Printing device 1102 captures the code for public PIN 1112 as sends it to public server 1004.

Step 1418 executes by associating public PIN 1112 with corporate PIN 1108 and the unprinted portion of document 1012, shown as document 1012B. Public PIN 1112 does not have to be verified by another application of policy 1010. Step 1420 executes by retrieving the unprinted portion by public server 1004 based on the information provided by transaction 1206. Step 1422 executes by sending the unprinted portion of document 1012 to printing device 1102.

Step 1424 executes by printing the portion, or document 1012B, at printing device 1102. The combination of document 1012A and document 1012B should provide the print job of document 1012. Step 1426 executes by sending transaction 1214 generated by printing device 1102 to public server 1004. Transaction 1214 may indicate that the print job is complete. In some embodiments, if another stoppage occurs, then transaction 1214 may indicate remaining unprinted portion of document 1012 that needs another public PIN to use at another printing device.

Step 1428 executes by deleting the PINs from public server 1004 and mobile application 1106 so that they cannot be used again. In some embodiments, corporate PIN 1108 may stay on public server 1004 but another request to print document 1012 may need to go to private server 1002 to apply policy 1010. Step 1430 executes by updating ledger 1003 with the statistics of the print job, such as pages printed, costs incurred, and the like.

FIG. 15 depicts a flowchart 1500 for receiving a public PIN at a printing device according to the disclosed embodiments. Flowchart 1500 may relate to step 1324 of flowchart 1300 and step 1416 of flowchart 1400 disclosed above. These steps disclose receiving public PIN 1110 or 1112 at a printing device. The public PIN may be entered or transmitted to the printing device. For the purposes of flowchart 1500, the disclosed embodiments may refer to public PIN 1112 and printing device 1102, which are used to print the unprinted portion of the document.

Step 1502 executes by receiving public PIN 1112 at mobile application 1106. The received public PIN corresponds to a corporate PIN 1108 for document 1012. Mobile application 1106 may store this relationship. Step 1504 executes by displaying public PIN 1112 on mobile device 1008 to the user. This step may be executed later as well. The user may want to verify that it is acceptable to print document 1012B for the unprinted pages.

Step 1506 executes by determining whether public PIN 1112 will be transmitted from mobile device 1008 to printing device 1102. As public PIN 1112 is a code, it may be provided to other devices as data. If yes, then step 1508 executes by sending public PIN 1112 to printing device 1102. In some embodiments, the public PIN may be sent over a network to an IP address associated with printing device 1102. In other embodiments, mobile device 1008 may connect to printing device 1102, either wired or wirelessly. Printing device 1102 receives public PIN 1112 using the features disclosed in FIG. 2. Step 1510 executes by confirming public PIN 1112 is acceptable. A verification message may be sent to mobile application 1106. Printing device 1102 also may confirm that public PIN 1112 is in an acceptable format to forward to public server 1004. If not, then an alert may be sent to the user through mobile application 1106.

If step 1506 is no, then step 1512 executes by entering the code for public PIN 1112 at printing device 1102. The user may punch in the code at operations panel 208 of printing device 1102. Printing device 1102 captures the entries and generates the information for the code to send to public server 1004. Step 1514 executes by generating a request for the unprinted portion of document 1012 to send. Step 1516 executes by sending the request with public PIN 1112 to public server 1004. Public server 1004 may respond with a confirmation of receipt of the request and that public PIN 1112 is acceptable to printing device 1102 or mobile application 1106. The remaining portion of the document is sent to printing device 1102 for printing operations.

As will be appreciated by one skilled in the art, the present invention may be embodied as a system, method or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, the present invention may take the form of a computer program product embodied in any tangible medium of expression having computer-usable program code embodied in the medium.

Any combination of one or more computer usable or computer readable medium(s) may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. Note that the computer-usable or computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

Computer program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an” and “the” are intended to include plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specific the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

Embodiments may be implemented as a computer process, a computing system or as an article of manufacture such as a computer program product of computer readable media. The computer program product may be a computer storage medium readable by a computer system and encoding a computer program instructions for executing a computer process. When accessed, the instructions cause a processor to enable other components to perform the functions disclosed above.

The corresponding structures, material, acts, and equivalents of all means or steps plus function elements in the claims below are intended to include any structure, material or act for performing the function in combination with other claimed elements are specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for embodiments with various modifications as are suited to the particular use contemplated.

One or more portions of the disclosed networks or systems may be distributed across one or more multi-functional printer (MFP) systems coupled to a network capable of exchanging information and data. Various functions and components of the MFP system may be distributed across multiple client computer platforms, or configured to perform tasks as part of a distributed system. These components may be executable, intermediate or interpreted code that communicates over the network using a protocol. The components may have specified addresses or other designators to identify the components within the network.

It will be apparent to those skilled in the art that various modifications to the disclosed may be made without departing from the spirit or scope of the invention. Thus, it is intended that the present invention covers the modifications and variations disclosed above provided that these changes come within the scope of the claims and their equivalents. 

1. (canceled)
 2. (canceled)
 3. (canceled)
 4. (canceled)
 5. (canceled)
 6. (canceled)
 7. (canceled)
 8. (canceled)
 9. (canceled)
 10. (canceled)
 11. A policy-based printing method comprising: sending a corporate personal identification number (PIN) entered into a mobile application on a mobile device to a public server, wherein the corporate PIN corresponds to a document stored on a private server connected to the public server; applying a policy stored at the private server to determine whether to print the document corresponding to the corporate PIN; receiving a first public PIN at the mobile application from the public server to print the document, wherein the first public PIN corresponds to the corporate PIN; receiving the first public PIN at the public server from a first printing device; printing a first portion of the document at the first printing device; determining that the first printing device is not available; receiving a second public PIN at the mobile application from the public server, wherein the second public PIN corresponds to the corporate PIN; receiving the second public PIN at the public server from a second printing device; printing a second portion of the document at the second printing device.
 12. The policy-based printing method of claim 11, further comprising entering the first public PIN at the first printing device.
 13. The policy-based printing method of claim 11, further comprising entering the second public PIN at the second printing device.
 14. The policy-based printing method of claim 11, further comprising receiving the corporate PIN at the private server from the public server.
 15. The policy-based printing method of claim 11, further comprising associating the policy to the first public PIN and the second public PIN.
 16. The policy-based printing method of claim 11, further comprising generating the corporate PIN at the private server when the document is stored on the private server.
 17. A policy-based printing system comprising: a mobile device configured to execute a mobile application; a private server storing a document and a corporate personal identification number (PIN) corresponding to the document, wherein a policy is applied to determine whether to print the document upon receipt of the corporate PIN at the private server, wherein the corporate PIN is provided to the mobile application; a public server connected to the private server and configured to send the corporate PIN upon receipt from the mobile device, wherein the public server generates a first public PIN upon receipt of the corporate PIN from the mobile application and sends the first public PIN to the mobile application; a first printing device to send the first public PIN to the public server and to print the document received from the public server, wherein the printing device indicates to the public server that printing operations are stopped and an unprinted portion of the document remains; the public server generates a second public PIN for the unprinted portion of the document and sends the second public PIN to the mobile application; and a second printing device to send the second public PIN to the public server and to print the unprinted portion of the document.
 18. The policy-based printing system of claim 17, further comprising a firewall between the private server and the public server.
 19. The policy-based printing system of claim 17, wherein the first printing device or the second printing device includes an operation panel to receive the first public PIN or the second public PIN, respectively.
 20. The policy-based printing system of claim 17, further comprising a websocket connection between the private server and the public server.
 21. A policy-based printing method comprising: receiving a corporate personal identification number (PIN) at a public server, wherein the corporate PIN corresponds to a document stored on a private server; generating a first public PIN corresponding to the corporate PIN at the public server; receiving the first public PIN at the public server from a first printing device; sending the document corresponding to the corporate PIN to the first printing device in response to the first public PIN; printing the document at the first printing device; stopping the print job of the document; generating a second public PIN at the public server corresponding to the corporate PIN, wherein the second public PIN refers to an unprinted portion of the document; receiving the second public PIN at the public server from a second printing device; sending the unprinted portion of the document to the second printing device; and printing the unprinted portion of the document at the second printing device.
 22. The policy-based printing method of claim 21, further comprising generating the corporate PIN at the private server upon receipt of the document.
 23. The policy-based printing method of claim 21, further comprising sending the first public PIN to a mobile application on a mobile device.
 24. The policy-based printing method of claim 21, further comprising sending a request for a print job of the document with the corporate PIN to the private server from the public server.
 25. The policy-based printing method of claim 21, wherein the corporate PIN, the first public PIN, or the second public PIN includes an alphanumeric code.
 26. The policy-based printing method of claim 21, further comprising receiving the first public PIN at the first printing device.
 27. The policy-based printing method of claim 21, further comprising receiving the second public PIN at the second printing device.
 28. The policy-based printing method of claim 21, further comprising deleting the first public PIN and the second public PIN from the public server.
 29. The policy-based printing method of claim 28, wherein the corporate PIN is not deleted from the public server.
 30. The policy-based printing method of claim 21, wherein the first public PIN differs from the second public PIN. 